Conditions

Conditions refer to the circumstances in which an asset operates. Conditions can affect a task's interval, or the frequency of a task. The adjustment percentage on a condition specifies the amount, in percentage, by which the task interval will be adjusted if that condition is applied. So, if an asset operates in a high-risk condition and tasks need to be performed more frequently, the adjustment percentage will be a negative value in order to decrease the task interval.

Linking conditions to an entity promotes an intelligent configuration, as assets and tasks will inherit these preconfigured conditions. Conditions are managed from the asset type tree but the functionality is actioned from the asset tree.

Conditions are available on the following entities:

  • Regular asset types
  • Placeholder asset types
  • Placeholder asset type components
  • Regular assets
  • Placeholder assets
  • Placeholder asset components.

Condition types are used as a grouping mechanism for related conditions. For example, a condition type called "Environment" is a classification used to group the environmental conditions in which an asset operates, such as "Summer", "Winter" and so on. If an asset operates in circumstances where the level of risk can vary, the condition type "Risk" could be used to classify conditions such as "High", "Medium" and "Low".

Configuring Conditions

The process for configuring conditions is as follows:

  1. Set up the master data for condition types and the associated conditions.
  2. Set Allow Conditions to true on the related asset type tree entity and associated regular asset type tasks, which have an interval type of either calendar-based or usage-based. Link the relevant conditions to the entity. The conditions are rolled out to the regular asset type tasks based on the criteria selected.
  3. Synchronise the asset tree. The conditions are inherited by the asset tree entities and regular asset tasks. Set the Active Condition on the condition related entities to specify the current conditions that must be applied. The active conditions are rolled out to the regular asset tasks.

Configure the master data for conditions so that they can be linked to the condition related asset type tree entities. Conditions are inherited by asset tree entities when they are synchronised. Based on the asset tree entities’ Active Condition, the frequency of tasks will be changed by applying an adjustment percentage . Conditions can be edited on any condition related entity and on all levels. When changes are made at any level, the changes can be applied to child entities based on the selected rollout criteria. Development statuses are used to accept the changes made. Changes can also be made manually at the individual level if customised changes are required.

Refer to the following sections for more information on conditions: Regular Asset Type Conditions, Regular Asset Type Task Conditions, Regular Asset Conditions and Regular Asset Task Conditions.

Keep in mind

Conditions synchronise from regular asset types to regular assets as per the normal synchronisation process.